AWS CodePipeline Review
Our IT Ops use AWS CodePipeline as a continuous delivery service in our company. We use it for easy and automated deployment of our …
Starting at $1 per active pipeline/per month
View PricingOverview
What is AWS CodePipeline?
AWS CodePipeline is a fully managed continuous delivery service that helps users automate release pipelines for fast, reliable application and infrastructure updates. CodePipeline automates the build, test, and deploy phases of the release process every time there is a code…
Recent Reviews
Reviewer Pros & Cons
Pricing
AWS CodePipeline
$1
Cloud
per active pipeline/per month
Free Tier
Free
Cloud
Entry-level set up fee?
- No setup fee
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Product Details
- About
- Tech Details
What is AWS CodePipeline?
AWS CodePipeline Technical Details
| Deployment Types | Software as a Service (SaaS), Cloud, or Web-Based |
|---|---|
| Operating Systems | Unspecified |
| Mobile Application | No |
Comparisons
Compare with
Reviews and Ratings
(32)Attribute Ratings
Reviews
(1-2 of 2)Companies can't remove reviews or game the system. Here's why
June 03, 2021
AWS CodePipeline Review
CodePipeline is used by many development teams across the company. We are a heavy GitHub Enterprise user, but those who are seeking a CI/CD type product that has a slick integration with GitHub AND native AWS support - those users always go to CodePipeline. It can also integrate with S3 which is a huge advantage for those who have code files deployed in AWS already and can blend them with files from their teams enterprise GitHub repos. Some of our users also rely on CodeCommit and have integrated CodePipeline with that service as well. The major problem it solves for us is ease of integration and the ability to fully automate + test a release.
- ease of use
- multiple service integrations
- option for container (ECS) support
- automatic change detection
- no local integration
- interface limitations
- time to setup
- API access
- GitHub Enterprise integration
- AWS native integrations
- workflow modeling
- reduced cost
- reduced 'man hours'
- lowered risk of pushing bad deployment
CodeCommit and CodeDeploy can be used with CodePipeline so it’s not really fair to stack them against each other as they can be quite the compliment. The same goes for Beanstalk, which is often used as a deployment target in relation to CodePipeline.
CodePipeline fulfills the CI/CD duty, where the other services do not focus on that specific function. They are supplements, not replacements. CodePipeline will detect the updated code and handle deploying it to the actual instance via Beanstalk.
Jenkins is open source and not a native AWS service, that is its primary differentiator. Jenkins can also be used as a supplement to CodePipeline.
January 17, 2020
AWS CodePipeline for easy deployment setup
AWS CodePipeline is one piece of several autoscaling back-end infrastructures I have launched in AWS. CodePipeline, in conjunction with CodeDeploy, allows for automated testing, building & deployment of Github & S3 hosted code. CodePipeline can be thought of the orchestrator of a typical AWS code deployment setup. It allows you to setup the source of the code change (S3/Github/etc) and then define the steps the code takes. For example, you can implement a build step using AWS CodeBuild. You can also implement test & deploy steps. By using CodeDeploy, you can keep a fleet of instances up-to-date with the latest code releases.
- CodePipeline reacts very quickly to new GitHub commits. It often starts new builds nearly instantly after code is pushed.
- The CodePipeline console & wizard is very intuitive. It was very easy to setup CodePipeline instances and define exactly required stages & the services to fulfill the stages.
- CodePipeline allows you to easily restart failed steps, right from the status page. The web console shows the current status of the builds and seems to not lag too far behind the actual status.
- If you are not using GitHub, the setup for integrating with a repository is complicated. Doesn't appear to offer support for other revision control services or other revision control tools out-of-the-box.
- CodePipeline is probably too expensive for personal projects, especially if you use the other AWS tools for the pipeline steps like CodeDeploy.
- Not as flexible or customizable as a self-hosted Jenkins server.
- CodePipeline has reduced ongoing devops costs for my clients, especially around deployment & testing.
- CodePipeline has sped up development workflow by making the deployment process automated off git pushes. Deployment takes very little coordination as the system will just trigger based on what is the latest commit in a branch.
- CodePipeline offered a lot of out-of-the-box functionality that was much simpler to setup than a dedicated CI server. It allowed the deployment process to built and put into production with much less and effort and cost compared to rolling the functionality manually.
I felt that, out of the alternatives, AWS CodePipeline was the simplest to setup and most reliable. Since my client's infrastructure was already hosted in AWS, I felt it was a no-brainer. If a client needed a similar solution with on-prem or non-AWS infrastructure, I would probably evaluate a different solution. AWS CodePipeline is pretty tightly coupled with the rest of the AWS ecosystem.